home *** CD-ROM | disk | FTP | other *** search
- Path: druid.borland.com!usenet
- From: Conrad Herrmann <cherrmann@wpo.borland.com>
- Newsgroups: comp.lang.c++
- Subject: Re: Does Borland share these MSVC++ problems?
- Date: Mon, 25 Mar 1996 11:33:19 -0800
- Organization: Borland International
- Message-ID: <3156F4FF.6EA5@wpo.borland.com>
- References: <4j2m6q$lg6@cnn.Princeton.EDU> <4j3udc$m6t@news1.h1.usa.pipeline.com> <3155CA30.11CC@airmail.net>
- NNTP-Posting-Host: walden.borland.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0GoldB1 (WinNT; I)
-
- Mark Nelson wrote:
- >
- > >
- > > >1. Do index variables declared in the for statement persist after the
- > > loop?
- > > >
- > > Yes, but this is subject to change in future releases as the new
- > > ANSI/ISO standard is implemented by the compiler developers.
- > > I have not yet received BC++5.0 (I got the books but no compiler) so
- > > I can not say how index vars are handled in that version.
- >
- > Borland C++ 5.0 limits the scope to the loop, as the standard dictates.
- > (Breaking code right and left, but it's not their fault!)
- > Mark,
- There is a switch to turn this off, if you want. For example,
- you have to use this switch to compile MFC....
-
- -- Conrad Herrmann
- (Borland C++)
-